collection

1.4.2. Vendor 7

Since this was our first real experience with CalConnect, we did not really have specific testing goals, but our focus was to get accounted with the people and products that were attending CalConnect. It was a real pleasure to meet all the people we got accounted with through the interoperability testing event. It was also good to get a better understanding of many of the clients customers will be using to interoperate with our application.

We really look forward to ongoing interactions with everyone we worked with through CalConnect. Below are notes I took on our interaction with specific vendors:

Vendor 3:

  • On single instance items, we are not showing the time zone for the item sent from another time zone. It is the correct time, but only shows the local time zone. (known issue)

  • When Vendor 3 changes the time of a meeting, the subject in our client connect through our server changes prepends Rescheduled, and the direct pop client does not put anything extra in the subject.

  • Auto Configuring a Vendor 8 profile through our application, connected with POP. It connected as IMAP. (investigating)

  • Default setting for meeting processing for Vendor 9 POP is turned off. I need to confirm this is expected for POP. (investigating)

  • Default setting on Vendor 8 POP is to decline on propose new time. I need to confirm this is expected for POP. (investigating)

Vendor 1:

  • Meeting request from Vendor 1 is not recognized as meeting requests and must be processed by opening .ics file which may or may not cause some of the other issues below. These cases all need to be confirmed with another client or once this issue is fixed.

  • Clicking Accept on ICS attachment for updated informational item does not send acceptance. Since it should be informational, we do not send an acceptance, but the buttons should not show up on informational update.

  • Informational update does not show as informational.

  • Decline an instance then receive an update for a new time on declined instance, and client does not prompt to send an acceptance.

  • Receiving a meeting update with attendee change where someone else is added, I am prompted to Accept. I would expect this to be informational.

  • Closing recurring ICS attachment prompts me to save on meeting request in inbox. This does not repro for single instance ICS file.

  • On meeting Cancellation, the processing of the cancellation removes the meeting from the calendar without clicking the Remove from calendar button.

  • Remove from Calendar on our server account on cancellation from Vendor 1 does not remove any instance from my calendar. This also happens when sent from Vendor 1 client. It did the right thing when sent from the server, but when sent from Vendor 1 it does not.

  • When our client accepts a Vendor 1 recurring meeting, the acceptance contains an attachment when viewed with Vendor 1’s client.

Vendor 2:

  • All interoperability cases we tried in the test event worked as expected.